Skip to content

Conversation

@ZJY0516
Copy link
Contributor

@ZJY0516 ZJY0516 commented Nov 12, 2025

Signed-off-by: zjy0516 <[email protected]>
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @ZJY0516, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the documentation for the Qwen3-Next model by introducing a new section dedicated to serving FP8 models. It provides users with detailed instructions and configurations to utilize 8-bit floating point acceleration techniques, such as flashinfer and TRT-LLM MoE, thereby improving the performance and efficiency of the Qwen3-Next-80B-A3B-Instruct-FP8 model.

Highlights

  • FP8 Model Support: Added a new section detailing how to serve FP8 (8-bit floating point) versions of the Qwen3-Next model.
  • Acceleration Techniques: Provided specific instructions for leveraging FP8 flashinfer trtllm MoE to accelerate model serving.
  • VLLM Configuration: Included a comprehensive vllm serve command block with necessary environment variables and compilation configurations for optimal FP8 performance.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the documentation for Qwen3-Next to include instructions for running the FP8 model. The changes are clear and add valuable information. I've made a couple of suggestions to improve clarity and consistency within the document.

Signed-off-by: zjy0516 <[email protected]>
Signed-off-by: zjy0516 <[email protected]>
Signed-off-by: zjy0516 <[email protected]>
Signed-off-by: zjy0516 <[email protected]>
Signed-off-by: zjy0516 <[email protected]>
@jeejeelee jeejeelee merged commit 0b7f899 into vllm-project:main Nov 12, 2025
2 checks passed
@ZJY0516 ZJY0516 deleted the qwen3-next branch November 12, 2025 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants